An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hey everyone, Starting to get a bit anxious here. Our app has been stuck in “In Review” for an unusually long time, and we haven’t received any updates or communication from Apple yet. Usually reviews are much faster for us, so this delay has us worried that something may be wrong or stuck in the process. We have an important release planned, and the uncertainty is honestly stressful. Has anyone else experienced unusually long review times recently? Did your app eventually go through, or did you have to contact Apple? Would really appreciate hearing others’ experiences. Thanks 🙏

As a game studio with real business commitments, we depend on a predictable App Review process. Every month, we publish updates, run user acquisition campaigns, and test new ideas; that’s how our business operates. It’s not optional. We have obligations to our partners, our marketing budgets are committed in advance, and our entire monthly rhythm depends on getting builds out on schedule. Right now, Apple’s App Review is making that impossible. For the past 30 days, we’ve been stuck in a rejection loop on a single submission. Here’s what the cycle looks like: • Apple rejects our build with vague, generic feedback that doesn’t actually identify what’s wrong. • We investigate every possible scenario that could conceivably match their description, fix what we believe is the issue, and resubmit, usually within three hours. • Then we wait. And wait. Each review of the resubmission takes more than ten days. Read that again: we respond in 3 hours, they respond in 2 weeks. This isn’t a one-off. It’s been three full cycles now, and we still don’t have clarity on what they actually want changed. The rejection notes are so shallow that we’re forced to guess; patch a plausible cause, ship it, and hope. It honestly feels like reviews are being triaged by AI models that aren’t ready for the job yet: surface-level pattern matching, no real engagement with the build, no specifics we can act on. Meanwhile, the cost is real: • UA campaigns we’ve already committed budget to are bleeding out. • Partner deliverables are slipping. • Our team’s monthly release rhythm — the engine of how we operate as a business — is broken. • We’re paying engineers to play guessing games with a reviewer who won’t tell us what’s wrong. We’ve escalated everywhere we can. Contact forms, appeals, developer support, every channel Apple offers. Nothing has moved. We love the platform. We want to keep shipping great games on iOS. But Apple needs to understand that App Review isn’t just a gatekeeping checkbox, it’s a load-bearing piece of every developer’s business operation. When a single rejection cycle eats 10+ days and the feedback isn’t actionable, you’re not protecting users. You’re breaking the businesses building for your platform. Two things need to change, urgently: 1. Restore meaningful, specific rejection feedback. Tell us exactly what’s wrong, with reproduction steps. If a human reviewer can’t be specific, an AI definitely shouldn’t be making the call. 2. Prioritize resubmissions on an in-flight review. A 10-day turnaround on a fix to a rejection you issued, three hours earlier, is indefensible. These should jump the queue, not start at the back. If anyone at Apple is reading this: we’re trying to work with you. Please help us help you. Want me to tighten it, make it angrier, soften it, or pull out the bullet lists so it reads as straight prose for the forum?

Hi App Review team, My app BadyApp (Badminton Group Management) has been stuck in "Waiting for Review" since May 12, 2026 and has never moved to "In Review" — no reviewer has engaged with it at all. Submission details: App Name: BadyApp Apple ID: 6762489731 Submitted: May 12, 2026 Current status: Waiting for Review (8+ days, no movement) Steps already taken: Submitted Apple Developer Support request at ~80 hours — no response received Resolution Center shows no messages Demo credentials provided in submission Privacy policy URL is active and accessible This is a straightforward badminton group management app with no sensitive permissions. The complete silence — no rejection, no message, no status change — suggests a possible system or queue hold that needs investigation. Could someone from the App Review team please look into this? Happy to provide any additional information. Thank you.

I had the issue pop up again. To refresh what previously happened, when I would submit a new build to TestFlight, it wouldn’t let me download it. That was a problem for a couple weeks. Then after the problem resolved I was able to download the “new build” but when I went into the app, it was clearly an old one. This issue got resolved a couple weeks ago, now it’s back. When I went to test out the new build on a couple of my apps, I was able to download it, but when I looked through the app, it was an old one. Please help me resolve this fast. Last time I waited for over a month

Hey All, Having a terrible time trying to submit subscriptions to the App Store. Any help or guidance would be much appreciated. Setup Auto-renewable subscriptions (Monthly + Annual) and one non-consumable (Lifetime), all attached to first binary submission RevenueCat for IAP infrastructure What happened First submission (v2.26): all three IAPs attached cleanly to the binary submission via the "In-App Purchases and Subscriptions" section on the version page. Apple's review came back with feedback on the paywall display (Guideline 3.1.2c - auto-renewable subscription prices not visible). The reviewer's screenshot showed Lifetime rendering correctly with a price, but the two subscription rows blank. I was missing a localization setting, which I then fixed. The localization went into Waiting for Review, then back to Rejected again within hours - App Store Connect's UI explains this: items attached to a rejected app version submission cannot independently progress through review. I then cancelled the v2.26 submission, which freed the localization to be re-submitted standalone. That stuck. I built a new binary (v2.27) and uploaded to App Store Connect. When I opened the v2.27 version page, the "In-App Purchases and Subscriptions" section that Apple's documentation describes (and which appeared on v2.26) was no longer present. I couldn't find any UI way to attach the subscriptions to this version's submission. The subscriptions and localization remained in Waiting for Review from earlier, and the Draft Submission panel for v2.27 only listed the binary. I submitted the binary alone in the hope that Apple's backend would bundle the in-queue subs with this version's review (since they all reference v2.27). Apple's reviewer reported the same display behaviour I see in my own testing - Annual/Monthly blank, Lifetime shown - and rejected on Guideline 2.1(b). What I've tried Resaving + resubmitting the group and per-subscription localizations Replying via Resolution Center with detailed context Updated App Review notes explaining the dependency between the subs and the binary Re-recorded the paywall screen recording on the current build Confirmed Paid Apps Agreement is Active and Tax / Banking are complete Completed a previously-incomplete "Sharing Economy Reporting Regime" compliance row that was in Missing Info (doesn't apply to my app, but flagged complete to rule it out) Sandbox testing on the iOS simulator with a sandbox tester signed in via Developer → Sandbox Apple Account: Lifetime renders its price, Monthly/Annual remain blank (same as Apple's review environment) Verified all product configuration in App Store Connect - pricing across territories, intro offers, localized display names + descriptions, review screenshots are all present Verified the RevenueCat offering correctly references the product IDs and the "pro" entitlement is properly linked Questions Is there a way to surface the "In-App Purchases and Subscriptions" attachment section on a new version after the first version was rejected? Something I'm missing in the configuration? For subscriptions sitting in Waiting for Review that are tied to a now rejected version, is there a way to attach them to a new version submission so they're reviewed together? If recreate with new IDs is the only path, is there any way to preserve the original product IDs for the subscription identifiers eventually, or are they permanently consumed? Thanks all, Cheers r

Hi Apple, I hope you are doing well. I am posting here regarding my app, Subscription & Expense Manager (App ID: 6759901202), which has been stuck in the “Waiting for Review” state since March 4, 2026 at 2:45 PM. It has now been an extremely long time without any update, review progress, or communication from the App Review team, and I am becoming increasingly concerned about this unusual delay. I completely understand that review times may vary depending on workload and internal processes, but this duration seems far beyond normal review timelines. Our team has invested substantial time, effort, and resources into developing this application, and the continued delay is significantly affecting our launch plans and business timeline. We have carefully followed all App Store Review Guidelines and ensured that every required detail, asset, permission, and compliance item was properly submitted. At the moment: There are no rejection messages No metadata issues are shown No additional information requests are pending The app simply remains stuck in “Waiting for Review” We have also already contacted Apple regarding this matter but unfortunately have not yet received a response. I would sincerely appreciate it if someone from Apple or the developer community could guide me on: Whether this kind of delay is currently common If there is any way to escalate the issue Whether there may be an unseen issue causing the review to not start We are fully prepared to provide any additional information or make immediate changes if required from our side. This app is very important to us, and we are genuinely worried because of the extended delay after putting so much hard work into the project. Any help, advice, or update would be greatly appreciated. Thank you. HR Apps

Hi Team, My App : LuvLust: Couples Game & Quiz (App ID: 6747910861) has been stuck in "Waiting for Review" for 3-4 weeks with no movement, no feedback, and no communication. What I've tried: Multiple expedited review requests & resubmissions although I understand now that's not the best way as it resets my position. I understand there are lot of requests but a queue number or some form of communication would help. Just want to know if there is a system glitch, account flag, or hidden blocker preventing my submission from entering review. Any help from the App Review team would be greatly appreciated. Thank you.

My app has been stuck in the “Waiting for Review” stage for the past 9 days, and I have not received any updates, feedback, or rejection notices. I have already contacted support multiple times regarding this issue, but unfortunately I have not received a response yet. I have spent a significant amount of time and resources building this app, including purchasing the required Apple Developer subscription and preparing everything according to the App Store guidelines. I kindly request you to please check my submission status or let me know if there is any issue causing the delay. Even a small update would be greatly appreciated. Case ID: 102893147964

Our application（Apple ID：6743150642） has been stuck in the Waiting for Review status for more than 7 days. We submitted an expedited review request 22 hours ago, but have not yet received a response. We are currently under significant time pressure, as our company’s app is required to launch before the Labor Day holiday. We have recently submitted a new version (1.2.0) and provided the institutional account as requested by the review team. We sincerely hope the expedited review request can help facilitate the process and move the review forward as soon as possible. Thank you for your attention and assistance.

Our application（Apple ID：861891048）has been stuck in the Waiting for Review status for more than 7 days(with an earlier version stuck in the same stage for another 7days). We submitted an expedited review request 3 days ago, and send an support email 2 days ago notify us it's been noticed, but nothing happens after. We were supposed to launch the new version along with our in-app event for the 20th May(520), now everything is left behind. We sincerely hope the expedited review request can help facilitate the process and move the review forward as soon as possible. We are gladly to offer any help or information to support. Thank you for your attention and assistance.

Hello App Review team, I am an iOS developer and my app (App ID: 6761247061) has been stuck in 'Waiting for Review' for nearly a week since May 15. Our previous submissions have always entered 'In Review' very quickly, so this is the first time we are experiencing such an extended delay. We have already tried the following: Opened a support case on May 18 (no response yet) Submitted a request for a call with App Review on May 21 We are sincerely hoping for any update or guidance from your team. If there is anything we have done incorrectly, we humbly ask that you let us know. We are fully prepared to make any change necessary to comply with the Review Guidelines. Any guidance or assistance would be deeply appreciated. Thank you!

My app submission is currently stuck in “Waiting for Review.” The latest build was submitted on May 14, 2026, but as of today it has still not moved into review. The App ID is 6760754970. We have checked the build, review notes, demo account, backend availability, in-app purchase configuration, and privacy information. Everything appears to be complete and accessible. Could someone from Apple please help confirm whether there is any issue with this submission, or whether any additional information is required from our side? We would appreciate your help in looking into this issue. Thank you.

Hi everyone, I'm submitting my watchOS-only app and its In-App Purchase for the very first time (both app and IAP submitted simultaneously). After multiple rejections, I still can't resolve the issue and would appreciate any guidance. Environment: App type: watchOS-only (no iOS companion app) First submission of both the app and IAP IAP type: Non-Consumable, Product Apple ID: 6770497337 The problem: The reviewer (App Review) states that the IAP product information cannot be retrieved in the review environment. According to the reviewer, they are testing in the production environment, not the sandbox. However: In my TestFlight build, the app correctly retrieves the IAP product I have successfully completed the full purchase flow using a sandbox account All business agreements (including Paid Apps Agreement) are accepted and active in The Bundle ID and Product ID are correctly configured in both Xcode and App Store Connect Current IAP status in App Store Connect: Overall status: "Developer Action Needed" All localizations (English US/UK/AU/CA, Japanese, Simplified Chinese, Traditional Chinese): "Rejected" No specific rejection reason is shown anywhere in App Store Connect Any help would be greatly appreciated. Thank you! 🙏

Hi, My app (6766506951) has been in review for two weeks with no status update. I already emailed the App Review team and submitted an expedited review request last week, but I haven’t received any response and the status is still “Waiting for Review.” I’m not sure what else I should do at this point. I would really appreciate your help.

Hello, I’m looking for guidance on a first auto-renewable subscription review issue that appears to be stuck. Our app “Skinora: AI Skincare Routine” has already been approved and is live on the App Store, but both of our first auto-renewable subscriptions are still stuck in “In Review”. App version: 1.0.1 Build: 6 Subscriptions: Skinora Pro Annual — product ID: skinora_pro_annual Skinora Pro Weekly — product ID: skinora_pro_weekly_Access Current App Store Connect state: App version 1.0.1 is approved/live Subscription group localization is Approved Both subscription products still show In Review There are no visible Resolution Center messages or Notes from App Review requiring action from us Background: The subscriptions were originally returned because the first subscriptions needed to be submitted with a new app version/binary. We then submitted them together with app version 1.0.1 build 6. The app was approved, but the subscriptions have remained In Review for several working days. (8 days) This is blocking our launch because the live app depends on these subscriptions for Pro access, and users cannot purchase/unlock Pro until Apple approves the products. I have already contacted Apple Developer Support multiple times and also called support. The support representative said they would escalate it internally, but the status has not changed yet. Is this a known App Store Connect issue with first auto-renewable subscriptions? Is there any way to confirm whether the subscriptions are actually being reviewed or stuck in an inconsistent state? Should I continue waiting, or is there a specific action needed to reset or move the subscription review forward? Any guidance would be appreciated.

Hello App Review team - I am an iOS developer and my app(App ID: 6756242440) is stuck in 'Waiting for review'. Please help us resolve the issue. Thanks in advance!

Hello, respected Apple Developer Forums community. SKU: com.apatura.safenet Apple ID: 6762392582 I am writing here because for almost a month we have not been able to find a solution to the situation with publishing our app, and I sincerely hope to get advice from other developers or Apple representatives. We are developing a VPN service. Initially, at an early stage, we tried to submit the app to the App Store from an individual Apple Developer account. Later, we understood that for this type of service we should use an organization account. Over time, the old Xcode project was lost. Because of that, we created a new project with the same name and similar visual materials, and submitted the app from the organization account. After that, the app was rejected under Guideline 4.3(a) — Design: Spam. The App Review message says that the app shares a similar binary, metadata, and/or concept with apps submitted to the App Store by other developers. We assume that the system may have linked the current submission to our previous submission from the individual account. It was in fact our own project, not an attempt to create a duplicate. We already explained this to the App Review Team in App Store Connect and provided information about the previous submission. We were even able to completely remove that app from App Store Connect under the individual account. We also explained that the current submission is being made from the organization account. After that, App Review requested additional information about the VPN functionality: what data the app collects, why it is used, and whether it is shared with third parties. We answered this in detail. However, after that we received the same rejection again under Guideline 4.3(a) — Design: Spam, without any additional explanation of what exactly we need to fix. We tried once again to explain that this is not spam and not a duplicate of someone else’s app. We also removed the old app record from the individual account so that it could no longer create a conflict or be detected as a possible duplicate. Now we are in a very difficult situation. We are not trying to bypass the rules. We are not publishing a network of identical apps. We are not using someone else’s template, and we are not trying to clutter the App Store. This is one real VPN service that we want to publish on behalf of the organization that operates it. It is very difficult when you wait several weeks for review, answer questions in detail, explain the situation, but then receive the same generic response again without understanding what exactly is wrong and what specifically needs to be done. We truly want to resolve this situation correctly, without conflict and without violating the rules. We just need a clear path forward. Apple Review Team, please read our thread in App Store Connect before replying with the same response again without real attention to the issue. I would be very grateful for any help, advice, or experience from developers who have faced a similar situation. With each new review, we wait 7–10 days and then receive the same generic replies without any real engagement. Thank you.

I want to share how I truly feel about this situation. I have spent years building every single app on my account before publishing anything on the App Store. Each one represents months of work, testing, and genuine effort to create something valuable for users. I am proud of what I built and I stand behind every app I have ever submitted. I honestly do not believe I deserve this decision. I have never intentionally violated any guideline. I have never tried to deceive Apple or users. I have always engaged with the review process in good faith, even when it was difficult and took months. The notice itself states that automation may have been used as part of the review process. I strongly believe this was an automated mistake. A human reviewer who looks carefully at my submission history and my apps will not find evidence of concept switching or hidden features; because there is none. I am a student in France. This account is how I support myself. Losing it overnight, after years of work, without a proper human review, is devastating. I am not asking for special treatment. I am asking for a fair human review of my case before a final decision is made. Thank you for reading this.

I am unable to submit any app for review. Every attempt to add a build to an App Store version results in a 409 error, both through the App Store Connect website and directly through the App Store Connect REST API. Affected accounts: Account 1: My personal Apple Developer account Account 2: A company-owned Apple Developer account where I have Admin access Both accounts are completely separate — different legal entities, different enrollments — but exhibit the exact same behavior simultaneously. API errors observed When calling PATCH /v1/appStoreVersions/{id}/relationships/build: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "The specified pre-release build could not be added." When calling POST /v1/appStoreVersions to create a new version: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "You cannot create a new version of the App in the current state." What I have verified All builds are processingState: VALID and not expired usesNonExemptEncryption: false is set on all builds No build is already attached to another version Build version string matches the App Store version (1.1.0) App bundle ID matches the build bundle ID Localization, review contact details, and keywords are all filled in Banking info in Agreements, Tax, and Banking was recently updated on both accounts Issue persists on both the website and via the REST API, ruling out a browser/cache issue Question Has anyone seen 409 errors affecting two completely separate developer accounts simultaneously? Could there be a platform-level issue with App Store Connect that is not reflected on the System Status page? I opened a support ticket 1 week ago but I only got a reply today and it's just asking for more details.

This is my first time submitting an app for review. I'm unable to submit my iOS app for review due to a persistent 409 error when trying to attach a build to my App Store version record. This has been happening across multiple builds and version strings. { "errors": [{ "id": "80550434-590c-48c6-b2d3-5bd3b038539b", "status": "409", "code": "ENTITY_ERROR.RELATIONSHIP.INVALID", "title": "The provided entity includes a relationship with an invalid value", "detail": "The specified pre-release build could not be added.", "source": { "pointer": "/data/relationships/build" } }] } What I've tried: • Submitted build 34 (version 1.0) — same 409 error • Incremented to build 35, version 1.0.1 — same 409 error • Removed the build from the version page and re-added it — same error Environment: • Xcode 16 • iOS deployment target: 17.0 • Builds processed successfully in TestFlight (status: Ready to Submit) • Version record ID: 198605a5​-2671​-44d6​-bacb​-04157088319d Question: Has anyone encountered this? Is the version record itself corrupted/stuck? The builds show as valid in TestFlight but cannot be attached to the App Store version.